-
Notifications
You must be signed in to change notification settings - Fork 507
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update snapshot-restore.md #4655
Update snapshot-restore.md #4655
Conversation
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. Signed-off-by: Sander van de Geijn <[email protected]>
Thanks, @ict-one-nl! @bowenlan-amzn Could you tech review this PR please? |
@jed326 Would you be able to review this PR? |
@kolchfa-aws sorry for the late response. I still see this setting in the code: https://github.com/opensearch-project/OpenSearch/blob/e3542011cd9584c354405ba6cbf9a31ced7bc5ce/plugins/repository-s3/src/main/java/org/opensearch/repositories/s3/S3ClientSettings.java#L238-L243 @ict-one-nl can you provide some more details of how you did the setup? |
Okay, it's kind of weird; Config:
Remove the comment on s3.client.default.disable_chunked_encoding: Comment it out: everything is fine |
The reason why the exception occurs is because the plugin doesn't register support for the setting: Interestingly, if I go back to 1.0, it wasn't there either: Based on the commit where the setting was added: opensearch-project/OpenSearch@07cf2cb, it looks like you can't add it as a default for all repositories (i.e. as a cluster-level setting), but you can specify |
@ict-one-nl , are you able to confirm whether the setting works as part of a repository creation request? Regardless, I agree with this specific PR -- it shouldn't be documented as an opensearch.yml setting. |
I think we should probably document the |
Documented the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, @ict-one-nl!
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. Signed-off-by: Sander van de Geijn <[email protected]> Co-authored-by: kolchfa-aws <[email protected]> (cherry picked from commit 17977e4) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. Signed-off-by: Sander van de Geijn <[email protected]> Co-authored-by: kolchfa-aws <[email protected]> (cherry picked from commit 17977e4) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. (cherry picked from commit 17977e4) Signed-off-by: Sander van de Geijn <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: kolchfa-aws <[email protected]>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. Signed-off-by: Sander van de Geijn <[email protected]> Co-authored-by: kolchfa-aws <[email protected]> (cherry picked from commit 17977e4) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. Signed-off-by: Sander van de Geijn <[email protected]> Co-authored-by: kolchfa-aws <[email protected]> (cherry picked from commit 17977e4) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. Signed-off-by: Sander van de Geijn <[email protected]> Co-authored-by: kolchfa-aws <[email protected]> (cherry picked from commit 17977e4) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. Signed-off-by: Sander van de Geijn <[email protected]> Co-authored-by: kolchfa-aws <[email protected]> (cherry picked from commit 17977e4) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. Signed-off-by: Sander van de Geijn <[email protected]> Co-authored-by: kolchfa-aws <[email protected]> (cherry picked from commit 17977e4) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. (cherry picked from commit 17977e4) Signed-off-by: Sander van de Geijn <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: kolchfa-aws <[email protected]>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. (cherry picked from commit 17977e4) Signed-off-by: Sander van de Geijn <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: kolchfa-aws <[email protected]>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. (cherry picked from commit 17977e4) Signed-off-by: Sander van de Geijn <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: kolchfa-aws <[email protected]>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. (cherry picked from commit 17977e4) Signed-off-by: Sander van de Geijn <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: kolchfa-aws <[email protected]>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. (cherry picked from commit 17977e4) Signed-off-by: Sander van de Geijn <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: kolchfa-aws <[email protected]>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. (cherry picked from commit 17977e4) Signed-off-by: Sander van de Geijn <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: kolchfa-aws <[email protected]>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. (cherry picked from commit 17977e4) Signed-off-by: Sander van de Geijn <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: kolchfa-aws <[email protected]>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. (cherry picked from commit 17977e4) Signed-off-by: Sander van de Geijn <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: kolchfa-aws <[email protected]>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. (cherry picked from commit 17977e4) Signed-off-by: Sander van de Geijn <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: kolchfa-aws <[email protected]>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. (cherry picked from commit 17977e4) Signed-off-by: Sander van de Geijn <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: kolchfa-aws <[email protected]>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. (cherry picked from commit 17977e4) Signed-off-by: Sander van de Geijn <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: kolchfa-aws <[email protected]>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. (cherry picked from commit 17977e4) Signed-off-by: Sander van de Geijn <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: kolchfa-aws <[email protected]>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. Signed-off-by: Sander van de Geijn <[email protected]> Co-authored-by: kolchfa-aws <[email protected]>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting. Signed-off-by: Sander van de Geijn <[email protected]> Co-authored-by: kolchfa-aws <[email protected]>
Setting seems deprecated. With it present clusters fails to start with message it does not recognise this setting.
Description
Describe what this change achieves.
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.